home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Oh!X 2001 Spring
/
Oh!X 2001 Spring Special CD-ROM (Japan).7z
/
Oh!X 2001 Spring Special CD-ROM (Japan) (Track 1).bin
/
NETBSD
/
INSTALL
Wrap
Text File
|
1998-12-14
|
75KB
|
2,113 lines
INSTALLATION NOTES for NetBSD/x68k 1.3.3
Be sure to read _ALL_ of this document before you try to install
NetBSD/x68k.
What is NetBSD?
---- -- ------
The NetBSD Operating System is a fully functional UN*X-like system
derived from the Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite,
and 4.4BSD-Lite2 sources. NetBSD runs on many architectures and is
being ported to more.
NetBSD is a creation of the members of the Internet community.
Without the unique cooperation and coordination the net makes
possible, it's likely that this release wouldn't have come about.
The NetBSD 1.3.3 release is a security and bug fix update for the
NetBSD 1.3 release.
The NetBSD 1.3 release was a landmark. Building upon the successful
NetBSD 1.2 release, we have provided numerous and significant
functional enhancements, including support for many new devices,
integration of many bug fixes, new and updated kernel subsystems, and
many userland enhancements. The results of these improvements is a
stable operating system fit for production use that rivals most
commercially available systems.
It is impossible to summarize the 18 months of development that went
into the NetBSD 1.3 release. Some of the significant changes include:
Support for machine independent device drivers has been
radically improved with the addition of the "bus.h" interface,
providing a high quality abstraction for machine and
architecture independent device access.
The bus_dma interface has also been integrated, providing a
machine-independent abstraction for DMA mapping. This permits many
good things, including (among many) clean multi-platform
bounce buffer support.
Framework support for ISA "Plug and Play" has been added, as
well as support for numerous "Plug and Play" devices.
APM support has been added to NetBSD/i386.
An initial cut of multi-platform PCMCIA support has been added.
Support for ATAPI devices (initially just ATAPI CD-ROM drives)
has been added.
Support for Sun 3/80s (sun3x architecture) has been added.
Support for R4000 DECstations has been added.
Integration/merger of 4.4BSD Lite-2 sources into userland
programs has nearly been completed.
Most of userland now compiles with high levels of gcc warnings
turned on, which has lead to the discovery and elimination of
many bugs.
The i386 boot blocks have been completely replaced with a new,
libsa based two stage boot system. This has permitted
integration of compressed boot support (see below).
Many ports now support booting of compressed kernels, and
feature new "Single Floppy" install systems that boot
compressed install kernels and ramdisks. We intend to do
substantial work on improving ease of installation in the
future.
"ypserv" has been added, thus completing our support for the
"yp" network information system suite.
Support for the Linux "ext2fs" filesystem and for FAT32 "msdosfs"
filesystems has been added.
TCP now has a SYN "compressed state engine" which provides
increased robustness under high levels of received SYNs (as in
the case of "SYN flood" attacks.) (Much of this code was
derived from sources provided by BSDI.)
An initial implementation of Path MTU discovery has been
integrated (though it is not turned on by default).
An initial kernel based random number generator pseudodevice has
been added.
Several major fixes have been integrated for the VM subsystem,
including the fix of a notorious VM leak, improved
synchronization between mmap()ed and open()ed files, and
massively improved performance in low real memory conditions.
A new swap subsystem has radically improved configuration and
management of swap devices and adds swapping to files.
Userland ntp support, including xntpd, has been integrated.
The audio subsystems have been substantially debugged and
improved, and now offer substantial emulation of the OSS audio
interface, thus providing the ability to cleanly run emulated
Linux and FreeBSD versions of sound intensive programs.
A "packages" system has been adapted from FreeBSD and will
provide binary package installations for third party
applications.
The XFree86 X source tree has been made a supported part of
the NetBSD distribution, and X servers (if built for this
port), libraries and utilities are now shipped with our releases.
The ftp(1) program has been made astoundingly overfunctional.
It supports command line editing, tab completion, status bars,
automatic download of URLs specified on the command line,
firewall support and many other features.
All ports now use "new" config. Old config has been laid to rest.
The ARP subsystem and API has been rewritten to make it less
ethernet-centric.
A new if_media subsystem has been added which allows network
interfaces to be configured using media type names rather than
device-specific mode bits.
Many kernel interface manual pages have been added to manual
section 9.
Several ports support much more hardware.
Many updates to bring NetBSD closer to standards compliance.
Most third party packages have been updated to the latest stable
release.
As has been noted, there have also been innumerable bug fixes.
Kernel interfaces have continued to be refined, and more subsystems
and device drivers are shared among the different ports. You can look
for this trend to continue.
NetBSD 1.3 also includes some refinement to the NetBSD binary emulation
system (which includes FreeBSD, HP-UX, iBCS2, Linux, OSF/1, SunOS, SVR4,
Solaris and Ultrix compatibility), bringing NetBSD closer to the goal of
making the emulation as accurate as possible.
In the near future, we hope to integrate a fully rewritten Virtual
Memory subsystem, kernel threads, and SMP support.
NetBSD 1.3.3 is the second public release of NetBSD for the x68k platform.
The Future of NetBSD:
--- ------ -- ------
The NetBSD Foundation has been incorporated as a non-profit
organization. Its purpose is to encourage, foster and promote the
free exchange of computer software, namely the NetBSD Operating
System. The foundation will allow for many things to be handled more
smoothly than could be done with our previous informal organization.
In particular, it provides the framework to deal with other parties
that wish to become involved in the NetBSD Project.
The NetBSD Foundation will help improve the quality of NetBSD by:
* providing better organization to keep track of development
efforts, including co-ordination with groups working in
related fields.
* providing a framework to receive donations of goods and
services and to own the resources necessary to run the
NetBSD Project.
* providing a better position from which to undertake
promotional activities.
* periodically organizing workshops for developers and other
interested people to discuss ongoing work.
We hope to have regular releases of the full binary and source trees,
but these are difficult to coordinate, especially with all of the
architectures which we now support!
We hope to support even _more_ hardware in the future, and have a
rather large number of other ideas about what can be done to improve
NetBSD.
We intend to continue our current practice of making the
NetBSD-current development source available on a daily basis.
We intend to integrate free, positive changes from whatever sources
will provide them, providing that they are well thought-out and
increase the usability of the system.
Above all, we hope to create a stable and accessible system, and to be
responsive to the needs and desires of NetBSD users, because it is for
and because of them that NetBSD exists.
Sources of NetBSD:
------- -- ------
NetBSD Mirror Site List
The following sites mirror NetBSD as of December 01, 1998.
If you wish to become a distribution site for NetBSD, contact
mirrors@netbsd.org.
FTP mirrors
-----------
Australia
* ftp.au.netbsd.org
RMIT University, Melbourne
ftp://ftp.au.netbsd.org/pub/NetBSD
* ftp2.au.netbsd.org
University of Queensland, Brisbane
ftp://ftp2.au.netbsd.org/pub/NetBSD
Austria
* ftp.at.netbsd.org
University of Technology, Vienna
ftp://ftp.at.netbsd.org/pub/NetBSD
Brazil
* ftp.ravel.ufrj.br
Cidade Universitaria
ftp://ftp.ravel.ufrj.br/pub/NetBSD
Denmark
* ftp.dk.netbsd.org
Aalborg University
ftp://ftp.dk.netbsd.org/pub/NetBSD
Finland
* ftp.fi.netbsd.org
The Finnish University and Research Network, Espoo
ftp://ftp.fi.netbsd.org/pub/NetBSD
France
* ftp.fr.netbsd.org
Paris University
ftp://ftp.fr.netbsd.org/pub/NetBSD
Germany
* ftp.de.netbsd.org
University of Trier
ftp://ftp.de.netbsd.org/pub/NetBSD
* ftp2.de.netbsd.org
University of Erlangen-Nuremberg
ftp://ftp2.de.netbsd.org/pub/NetBSD
* ftp.uni-regensburg.de
University of Regensburg
ftp://ftp.uni-regensburg.de/pub/comp/os/NetBSD
Japan
* ftp.jp.netbsd.org
Internet Research Institute Inc., Tokyo
ftp://ftp.jp.netbsd.org/pub/NetBSD
* ftp.dti.ad.jp
ftp://ftp.dti.ad.jp/pub/NetBSD/
* mirror.nucba.ac.jp
Nagoya University of Commerce and Business
ftp://mirror.nucba.ac.jp/mirror/NetBSD
* netbsd.tohoku.ac.jp
Tohoku University
ftp://netbsd.tohoku.ac.jp/NetBSD
Korea
* sunsite.kren.ne.kr
Seoul National University
ftp://sunsite.kren.ne.kr/pub/OS/NetBSD
Netherlands
* ftp.nl.netbsd.org
University of Amsterdam
ftp://ftp.nl.netbsd.org/pub/NetBSD
Norway
* ftp.no.netbsd.org
ftp://ftp.no.netbsd.org/pub/NetBSD
* ftp.ntnu.no
Norwegian University of Science and Technology
ftp://ftp.ntnu.no/pub/NetBSD
* skarven.itea.ntnu.no
Norwegian University of Science and Technology
ftp://skarven.itea.ntnu.no/pub/NetBSD
Russia
* ftp.ru.netbsd.org
Landau Institute for Theoretical Physics, Chernogolovka
ftp://ftp.ru.netbsd.org/pub/NetBSD
Sweden
* ftp.stacken.kth.se
Royal Institute of Technology, Stockholm
ftp://ftp.stacken.kth.se/pub/OS/NetBSD
* ftp.sunet.se
Swedish University NETwork, Uppsala
ftp://ftp.sunet.se/pub/os/NetBSD
UK
* ftp.uk.netbsd.org
Domino, London
ftp://ftp.uk.netbsd.org/pub/NetBSD
* sunsite.org.uk
ftp://sunsite.org.uk/packages/netbsd
USA
* ftp.netbsd.org
Silicon Valley, California
ftp://ftp.netbsd.org/pub/NetBSD
* ftp.cs.umn.edu
University of Minnesota
ftp://ftp.cs.umn.edu/pub/NetBSD
* ftp.eecs.umich.edu
University of Michigan, Ann Arbor
ftp://ftp.eecs.umich.edu/pub/NetBSD
* ftp.iastate.edu
Iowa State University
ftp://ftp.iastate.edu/pub/netbsd
* ftp.op.net
ftp://ftp.op.net/pub/NetBSD
AFS mirrors
-----------
Sweden
* ftp.stacken.kth.se
Royal Institute of Technology, Stockholm
AFS path: /afs/stacken.kth.se/ftp/pub/OS/NetBSD
USA
* ftp.iastate.edu
Iowa State University
AFS path: /afs/iastate.edu/public/ftp/pub/netbsd
NFS mirrors
-----------
UK
* sunsite.org.uk
Instructions: mount -o ro sunsite.org.uk:/public/packages/netbsd /mnt
SUP mirrors
-----------
Australia
* sup.au.netbsd.org
RMIT University, Melbourne
Instructions: ftp://sup.au.netbsd.org/pub/NetBSD/sup/README.sup
France
* sup.fr.netbsd.org
Paris University
Instructions: Similar to sup.netbsd.org
Germany
* sup.de.netbsd.org
University of Trier
Instructions: ftp://sup.de.netbsd.org/pub/NetBSD/sup/supfile.example
* sup.owl.de
Instructions: ftp://sup.owl.de/pub/sup/supfile.example
Japan
* sup.jp.netbsd.org
Internet Research Institute Inc., Tokyo
Instructions: ftp://sup.jp.netbsd.org/pub/NetBSD/sup/README.sup
Norway
* skarven.itea.ntnu.no
Norwegian University of Science and Technology
Instructions: Use this line as your sup file to get /usr/README.supinfo-
skarven:current release=supinfo host=skarven.itea.ntnu.no use-rel-suffix
backup delete old base=/usr prefix=/usr hostbase=/supmirror
UK
* sup.uk.netbsd.org
Domino, London
Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup
USA
* sup.netbsd.org
Silicon Valley, California
Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup
* ftp.cs.umn.edu
University of Minnesota
Instructions: hostbase=/ftp/ftp/packages/NetBSD, collections are the same
as on sup.NetBSD.ORG
WWW mirrors
-----------
Australia
* www.au.netbsd.org
RMIT University, Melbourne
http://www.au.netbsd.org/
Austria
* www.at.netbsd.org
University of Technology, Vienna
http://www.at.netbsd.org/
Finland
* www.fi.netbsd.org
Global Wire Oy, Lappeenranta
http://www.fi.netbsd.org/
France
* www.fr.netbsd.org
Paris University
http://www.fr.netbsd.org/
Germany
* www.de.netbsd.org
http://www.de.netbsd.org/
Japan
* www.jp.netbsd.org
Internet Research Institute Inc., Tokyo
http://www.jp.netbsd.org/
Norway
* www.no.netbsd.org
http://www.no.netbsd.org/
USA
* www.netbsd.org
Western Washington State University
http://www.netbsd.org/
* www2.us.netbsd.org
New York
http://www.us.netbsd.org/
NetBSD 1.3.3 Release Contents:
------ ----- ------- --------
The NetBSD 1.3.3 release is organized in the following way:
.../NetBSD-1.3.3/
BUGS Known bugs list (incomplete
and out of date).
CHANGES Changes since NetBSD's last
release (and before).
LAST_MINUTE Last minute changes.
MIRRORS A list of sites that mirror
the NetBSD 1.3.3 distribution.
README.files README describing the
distribution's contents.
TODO NetBSD's todo list (incomplete
and out of date).
patches/ Post-release source code
patches.
source/ Source distribution sets; see
below.
In addition to the files and directories listed above, there is one
directory per architecture, for each of the architectures for which
NetBSD 1.3.3 has a binary distribution. There are also
'README.export-control' files sprinkled liberally throughout the
distribution tree, which point out that there are some portions of the
distribution (i.e. the `domestic' portion) that may be subject to
export regulations of the United States. It is your responsibility
to determine whether or not it is legal for you to export these portions
and to act accordingly.
The source distribution sets can be found in subdirectories of the
"source" subdirectory of the distribution tree. They contain the
complete sources to the system. The source distribution sets
are as follows:
secrsrc.tgz:
This set contains the "domestic" sources. These
sources may be subject to United States export
regulations.
[ 412K gzipped, 1.8M uncompressed ]
gnusrc.tgz:
This set contains the "gnu" sources, including
the source for the compiler, assembler, groff,
and the other GNU utilities in the binary distribution
sets.
[ 15.6M gzipped, 66.4M uncompressed ]
syssrc.tgz:
This set contains the sources to the NetBSD 1.3.3
kernel, config(8), and dbsym(8).
[ 10.7M gzipped, 50.0M uncompressed ]
sharesrc.tgz:
This set contains the "share" sources, which include
the sources for the man pages not associated with
any particular program, the sources for the
typesettable document set, the dictionaries, and more.
[ 2.9M gzipped, 11.1M uncompressed ]
src.tgz:
This set contains all of the NetBSD 1.3.3 sources which
are not mentioned above.
[ 13.9M gzipped, 60.7M uncompressed ]
It is worth noting that unless all of the source distribution sets
are installed (except the domestic set), you can't rebuild and install
the system from scratch, straight out of the box. However, all that is
required to rebuild the system in that case is a trivial modification
to one Makefile.
Most of the above source sets are located in the source/sets
subdirectory of the distribution tree. The secrsrc.tgz set is
contained in the source/security subdirectory. This set, which is
available only to users in the United States and Canada, contains the
sources normally found in /usr/src/domestic -- primarily kerberos and
other cryptographic security related software. (Remember, because of
United States law, it may not be legal to distribute this set to
locations outside of the United States and Canada.)
The source sets are distributed as compressed tar files. They may be
unpacked into /usr/src with the command:
cat set_name.tgz | gunzip | (cd /; tar xpf - )
The sets/Split/ and security/Split/ subdirectories contain split
versions of the source sets for those users who need to load the
source sets from floppy or otherwise need a split distribution. The
split sets are are named "set_name.xx" where "set_name" is the
distribution set name, and "xx" is the sequence number of the file,
starting with "aa" for the first file in the distribution set, then
"ab" for the next, and so on. All of these files except the last one
of each set should be exactly 240,640 bytes long. (The last file is
just long enough to contain the remainder of the data for that
distribution set.)
The split distributions may be reassembled and extracted with "cat" as
follows:
cat set_name.?? | gunzip | (cd /; tar xpf - )
In each of the source distribution set directories, there is a file
named "CKSUMS" which contains the checksums of the files in that
directory, as generated by the cksum(1) utility. You can use cksum to
check the integrity of the archives, if you suspect that one of the
files is corrupt and have access to a cksum binary. Checksums based on
other algorithms may also be present -- see the release(7) man page
for details.
The x68k-specific portion of the NetBSD 1.3.3 release is found in the
"x68k" subdirectory of the distribution. That subdirectory is laid
out as follows:
.../NetBSD-1.3.3/x68k/
INSTALL Installation notes; this file.
binary/sets/ x68k binary distribution sets;
see below.
floppies/ x68k boot and installation
floppy; see below.
utils/ installation utilities which
runs on Human68k.
There is a floppy image in the "x68k/floppies" subdirectory of the
NetBSD 1.3.3 distribution, called "boot.fs". This can be used for both
installing NetBSD/x68k for the first time, and upgrading it from the
previous release. There is also gzipped version of this floppy (named
with ".fs.gz") available.
The NetBSD/x68k binary distribution sets contain the binaries which
comprise the NetBSD 1.3.3 release for the x68k. There are eight binary
distribution sets. The binary distribution sets can be found in the
"x68k/binary/sets" subdirectory of the NetBSD 1.3.3 distribution tree,
and are as follows:
base The NetBSD/x68k 1.3.3 base binary distribution. You
MUST install this distribution set. It contains the
base NetBSD utilities that are necessary for the
system to run and be minimally functional. It
includes shared library support, and excludes
everything described below.
[ 8.7M gzipped, 25.2M uncompressed ]
comp The NetBSD/x68k Compiler tools. All of the tools
relating to C, C++, Objective C, and FORTRAN (yes,
there are two, although NO FORTRAN compiler!).
This set includes the system include files
(/usr/include), the linker, the compiler tool chain,
and the various system libraries (except the shared
libraries, which are included as part of the base
set). This set also includes the manual pages for all
of the utilities it contains, as well as the system
call and library manual pages.
[ 6.5M gzipped, 22.8M uncompressed ]
etc This distribution set contains the system
configuration files that reside in /etc and in several
other places. This set MUST be installed if you are
installing the system from scratch, but should NOT be
used if you are upgrading. (If you are upgrading,
it's recommended that you get a copy of this set and
CAREFULLY upgrade your configuration files by hand.)
[ 53K gzipped, 330K uncompressed ]
games This set includes the games and their manual pages.
[ 2.8M gzipped, 7.0M uncompressed ]
kern This set contains a NetBSD/x68k 1.3.3 ALL kernel,
named "/netbsd". You MUST install this distribution
set.
[ 640K gzipped, 1.4M uncompressed ]
man This set includes all of the manual pages for the
binaries and other software contained in the base set.
Note that it does not include any of the manual pages
that are included in the other sets.
[ 2.4M gzipped, 9.8M uncompressed ]
misc This set includes the system dictionaries (which are
rather large), the typesettable document set, and
man pages for other architectures which happen to be
installed from the source tree by default.
[ 2.1M gzipped, 8.2M uncompressed ]
text This set includes NetBSD's text processing tools,
including groff, all related programs, and their
manual pages.
[ 1.0M gzipped, 3.7M uncompressed ]
IMPORTANT: In previous versions of NetBSD, the kernel from the install
floppy was copied onto the hard drive in a special step. In the new
install system, the kernel on the floppy is unsuited to being copied
onto the hard drive. Instead, a new set, "kern", has been added which
contains a generic kernel to be unloaded onto the drive. It must be
extracted in order to have a minimally functioning system.
For other platform, there is a security distribution named "secr"
provided. The x68k security distribution is not provided in the
binary form.
The x68k binary distribution sets are distributed as gzipped tar files
named with the extension ".tgz", e.g. "base.tgz".
The instructions given for extracting the source sets work equally
well for the binary sets, but it is worth noting that if you use that
method, the files are extracted "below" the current directory. That
is, if you want to extract the binaries "into" your system, i.e.
replace the system binaries with them, you have to run the "tar xpf"
from /. Also note that if you upgrade or install this way, those
programs that you are using at the time will NOT be replaced unless
you run "tar" with the "--unlink" option. If you follow the normal
installation or upgrade procedures, this will be taken care of for
you.
NetBSD System Requirements and Supported Devices:
------ ------ ------------ --- --------- -------
NetBSD/x68k 1.3.3 runs on the Sharp X68030 series PCs with TRUE
MC68030 MPU (not MC68EC030) and FPU. Since the processor of
the X68030 series is MC68EC030, you need to replace it with
MC68030 (Simply remove the old chip and put the new one instead.
instead. The largest difficulty might be to open your X68030).
In addition, some accelerators are supported:
Xellent30 series
040turbo
Jupiter-X (040 / 060)
060turbo
This means all models of X680x0 series PC except for CZ-600C
and CZ-674C, by using the appropriate accelerator, can run NetBSD!!
Note that the processor of Xellent30 series is MC68EC030, so
you need to replace your processor as well as for X68030.
The minimal configuration requires 4M of RAM and about 80M of
disk space. To install the entire system requires much more disk space,
and to run X or compile the system, more RAM is recommended.
Here is a table of recommended HD partition sizes for a full install:
partition: advise, with X, needed, with X
root (/) 20M 20M 15M 15M
user (/usr) 95M 125M 75M 105M
swap ----- 2M for every M ram -----
local (/local) up to you
As you may note the recommended size of /usr is 20M greater than
needed. This is to leave room for a kernel source and compile tree
as you will probably want to compile your own kernel. (ALL is
large and bulky to accommodate all people).
Supported devices include:
- Sharp genuine SCSI interface (builtin / optional)
* SCSI harddisks, CD-ROM drives, tape drives, scanners,...
- Mankai Seisakusho Mach-2 SCSI interface
- The builtin floppy drives
- The builtin frame buffer (both of the text and graphics screen)
- The builtin serial (RS-232C)
- The builtin parallel (Centronics printer interface)
- The standard keyboard
- The mouse / trackball
- NS16550 serial
- Neptune-X ethernet
Hopefully, the AD-PCM sound device will be supported on the next
release.
IMPORTANT NOTE: Xellent users *MUST* change the address map setting
for it from the default ($ECC000 - $ECFFFF) before installation. This
is because the default address conflicts with the Neptune-X ethernet
interface, and the Neptune driver is confused by it. All the settings
other than the default are ok. Once you installed NetBSD, and configured
your own kernel, you can restore the setting.
Getting the NetBSD System on to Useful Media:
------- --- ------ ------ -- -- ------ -----
Installation is supported from several media types, including:
Removable SCSI hard disk, or Magneto-Optical disk (MO)
Tape
Remote NFS partition
FTP
No matter which installation medium you choose, you'll need to have
a floppy disk. On the first, you'll put the install or upgrade floppy
image, depending on whether you're installing NetBSD for the first time,
or upgrading a previous installation.
If you are using a UN*X-like system to write the floppy images to
disks, you should use the "dd" command to copy the file system images
(.fs files) directly to the raw floppy disks. It is suggested that
you read the dd(1) manual page or ask your system administrator to
determine the correct set of arguments to use; it will be slightly
different from system to system, and a comprehensive list of the
possibilities is beyond the scope of this document.
If you are using Human68k to write the floppy images to disks, you should
use the "rawrite" utility, provided in the "x68k/utils" directory
of the NetBSD distribution. It will write the file system images (.fs
files) to disks.
Note that, when installing, the install floppy MUST not be write-protected.
The install program needs to write some temporary files, and if the
disk is write-protected, it can't. If you're upgrading your system,
the upgrade floppy may be write-protected.
Obviously, the steps necessary to prepare the distribution sets for
installation or upgrade depend on which installation medium you
choose. The steps for the various media are outlined below.
To install or upgrade NetBSD using
To install or upgrade NetBSD using a removable SCSI harddisk or MO,
you need to the following:
To install NetBSD from a removablethe media MUST be of the IBM
`Super-floppy' format. The Human68k format is not recognized
by this release of the NetBSD/x68k. If you have a MS-DOS (or
MS-Windows) machine with an MO drive connected, use it. If
you don't, and if you have a program to handle IBM format MO
for Human68k, copy all the files in the subdirectory
"x68k/binaries" and CHANGE THEIR NAMES IN UPPER CASE.
To install or upgrade NetBSD using a tape, you need to do the
following:
To install NetBSD from a tape, you need to make a tape that
contains the distribution set files, in "tar" format. If
you're making the tape on a UN*X-like system, the easiest way
to do so is probably something like:
tar cf <tape_device> <dist_directories>
where "<tape_device>" is the name of the tape device that
describes the tape drive you're using (possibly /dev/rst0, or
something similar, but it will vary from system to system.
(If you can't figure it out, ask your system administrator.)
In the above example, "<dist_directories>" are the
distribution sets' directories, for the distribution sets you
wish to place on the tape. For instance, to put the "base"
and "etc" distributions on tape (in order to do the absolute
minimum installation to a new disk), you would do the
following:
cd .../NetBSD-1.3.3 # the top of the tree
cd x68k/binary/sets
tar cf <tape_device> base.tgz etc.tgz
(Note that you still need to fill in "<tape_device>" in the
example.)
Once you have the files on the tape, you can proceed to the
next step in the installation or upgrade process. If you're
installing NetBSD from scratch, go to the section on preparing
your hard disk, below. If you're upgrading an existing
installation, go directly to the section on upgrading.
To install or upgrade NetBSD using a remote partition, mounted via
NFS, you must do the following:
NOTE: This method of installation is recommended only for
those already familiar with using BSD network
configuration and management commands. If you aren't,
this documentation should help, but is not intended to
be all-encompassing.
Place the NetBSD distribution sets you wish to install into a
directory on an NFS server, and make that directory mountable
by the machine on which you are installing or upgrading NetBSD.
This will probably require modifying the /etc/exports file on
of the NFS server and resetting its mount daemon (mountd).
(Both of these actions will probably require superuser
privileges on the server.)
You need to know the the numeric IP address of the NFS server,
and, if the server is not on a network directly connected to
the machine on which you're installing or upgrading NetBSD,
you need to know the numeric IP address of the router closest
to the NetBSD machine. Finally, you need to know the numeric
IP address of the NetBSD machine itself.
Once the NFS server is set up properly and you have the
information mentioned above, you can proceed to the next step
in the installation or upgrade process. If you're installing
NetBSD from scratch, go to the section on preparing your hard
disk, below. If you're upgrading an existing installation, go
directly to the section on upgrading.
To install or upgrade NetBSD by using FTP to get the installation
sets, you must do the following:
NOTE: This method of installation is recommended only for
those already familiar with using BSD network
configuration and management commands. If you aren't,
this documentation should help, but is not intended to
be all-encompassing.
The preparations for this installation/upgrade method are
easy; all you make sure that there's some FTP site from which
you can retrieve the NetBSD distribution when you're about to
install or upgrade. You need to know the numeric IP address
of that site, and, if it's not on a network directly connected
to the machine on which you're installing or upgrading NetBSD,
you need to know the numeric IP address of the router closest
to the NetBSD machine. Finally, you need to know the numeric
IP address of the NetBSD machine itself.
Once you have this information, you can proceed to the next
step in the installation or upgrade process. If you're
installing NetBSD from scratch, go to the section on
preparing your hard disk, below. If you're upgrading an
existing installation, go directly to the section on
upgrading.
If you are upgrading NetBSD, you also have the option of installing
NetBSD by putting the new distribution sets somewhere in your existing
file system, and using them from there. To do that, you must do the
following:
Place the distribution sets you wish to upgrade somewhere in
your current file system tree. At a bare minimum, you must
upgrade the "base" binary distribution, and so must put the
"base.tgz" set somewhere in your file system. If you wish,
you can do the other sets, as well, but you should NOT upgrade
the "etc" distribution; the "etc" distribution contains system
configuration files that you should review and update by hand.
Once you have done this, you can proceed to the next step in
the upgrade process, actually upgrading your system.
Preparing your System for NetBSD Installation:
--------- ---- ------ --- ------ ------------
NOTE: Currently NetBSD/x68k requires a dedicated disk when you install
it for the first time. In other words NetBSD/x68k cannot be installed
on the hard disk on which Human68k or any other operating systems
reside. This is because of the poor installer, and the system itself
can share a single disk with other OSs. This problem should be fixed
in the next release.
What you have to do to prepare the disk is only to physically format
your hard disk by using FORMAT.x utility of Human68k to install the
master boot program on your disk. You can now proceed with the
installation instructions.
Installing the NetBSD System:
---------- --- ------ ------
Installing NetBSD is a relatively complex process, but if you have
this document in hand and are careful to read and remember the
information which is presented to you by the install program, it
shouldn't be too much trouble.
Before you begin, you should know the geometry of your hard disk, i.e.
the sector size (note that sector sizes other than 512 bytes are not
currently supported), the number of sectors per track, the number of
tracks per cylinder (also known as the number of heads), and the
number of cylinders on the disk. The NetBSD kernel will try to
discover these parameters on its own, and if it can it will print them
at boot time. If possible, you should use the parameters it prints.
(You might not be able to because you're sharing your disk with
another operating system, or because your disk is old enough that the
kernel can't figure out its geometry.)
You should now be ready to install NetBSD. It might be handy for you
to have a pencil, some paper, and a calculator handy.
The following is a walk-through of the steps you will take while
getting NetBSD installed on your hard disk. If any question has a
default answer, it will be displayed in brackets ("[]") after the
question. If you wish to stop the installation, you may hit Control-C
at any time, but if you do, you'll have to begin the installation
process again from scratch.
Boot your machine using of boot floppy. If the boot prompt
does not appear in a reasonable amount of time, you either
have a bad boot floppy or a hardware problem. Try writing the
boot floppy image to a different disk, and using that. If it
still doesn't work, NetBSD probably can't be run on your
hardware. This can probably be considered a bug, so you might
want to report it. If you do, please include as many details
about your system configuration as you can.
It will take a while to load the kernel from the floppy,
probably around a minute or so.
You will then be presented with the NetBSD kernel boot
messages. You will want to read them, to determine your
disk's name and geometry. Its name will be something like
"sd0" and the geometry will be printed on a line that
begins with its name. As mentioned above, you will need your
disk's geometry when creating NetBSD's partitions. You will
also need to know the name, to tell the install tools what
disk to install on.
While booting, you will probably see several warnings. You
should be warned that no swap space is present, and that
init(8) cannot find /etc/rc. Do not be alarmed, these are
completely normal. When you reach the prompt asking you for a
shell name, just hit return.
You will be presented with a welcome message and a prompt,
asking if you wish to proceed with the installation process.
If you wish to proceed, enter "y" and hit return.
The install program will then tell you which disks it can
install on, and ask you which it should use.
Reply with the name of your disk.
You will then be asked to name your disk's disklabel. The
default response is "mysd", and for most purposes it will be
OK. If you choose to name it something different, make sure
the name is a single word and contains no special characters.
You don't need to remember this name.
You will be prompted for your disk's geometry information,
i.e. the number of bytes per sector, cylinders on the disk,
tracks per cylinder (heads), and sectors per track. Enter
them when they are requested. If you make a mistake, hit
Control-C and when you get to the shell prompt, restart the
install process by running the "install" command. Once you
have entered this data, the install program will tell you the
total size of your disk, in both sectors, and cylinders.
Remember this number; if you're installing on the whole disk,
you'll need it again soon.
When describing your partitions, you will have the option of
entering data about them in units of disk sectors or
cylinders. If you choose to enter the information in units of
sectors, remember that, for optimal performance, partitions
should begin and end on cylinder boundaries. You will be
asked about which units you wish to use, and you should reply
with "c" for cylinders, or "s" for sectors.
You will be asked to enter the size of your NetBSD root
partition. It should be at least 15M, but if you are going to
be doing development, 20M is a more desirable size. This
size should be expressed in units of sectors or cylinders,
depending on which you said you wanted to use.
Next, you will be asked for the size of your swap partition.
You should probably allocate twice as much swap space as you
have real memory. Systems that will be heavily used should
have more swap space allocated, and systems that will be
lightly used can get by with less. If you want the system to
be able to save crash dumps when it panics, you will need at
least as much swap space as you have RAM. Again, this number
should be expressed in units of sectors or cylinders, as
appropriate.
The install program will then ask you for information about
the rest of the partitions you want on your disk. For most
purposes, you will want only one more partition, "/usr".
(Machines used as servers will probably also want /var as a
separate partition. That can be done with these installation
tools, but is not covered here.) The install program will
tell you how much space there is left to be allocated in the
NetBSD area of the disk, and, if you only want one more
partition ("/usr"), you should enter it at the prompt when the
installer asks you how large the next partition should be.
It will then ask you for the name of the mount point for that
partition. If you're doing a basic installation, that is
"/usr".
YOU ARE NOW AT THE POINT OF NO RETURN. Nothing has been
written to your disk yet, but if you confirm that you want to
install NetBSD, your hard drive will be modified, and its
contents may be scrambled at the whim of the install program.
This is especially likely if you have given the install
program incorrect information. If you are sure you want to
proceed, enter "yes" at the prompt.
The install program will now label your disk and make the file
systems you specified. The filesystems will be initialized to
contain NetBSD bootstrapping binaries and configuration files.
It will also create an /etc/fstab for your system, and mount
all of the file systems under /mnt. (In other words, your root
partition will be mounted on /mnt, your /usr partition on
/mnt/usr, and so on.) There should be no errors in this
section of the installation. If there are, restart from the
beginning of the installation process.
You will be placed at a shell prompt ("#"). The remaining
tasks are to copy the kernel from the kernel copy floppy to
the hard drive's root filesystem and install the distribution
sets. The flow of installation differs depending on your
hardware resources, and on what media the distribution sets
reside.
To install from removable hard disk:
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, enter the command "Set_tmp_dir", and enter
the name of the temporary directory. (Don't forget
that your disk is mounted under /mnt; you should
probably pick a directory under /mnt/usr.) The
default is /mnt/usr/distrib.
Insert the media onto the drive. Check the device
name of your drive from the boot message. The device
name is something like "sd2" depending on the SCSI
disk drives connected to your machine. Note that the
boot message can be displayed with the command
"more /kern/msgbuf".
Mount the disk on the temporary directory with a
command like:
mount -t msdos /dev/sd2c <tmp_dir>
if your removable drive's name is sd2.
Run the "Extract" command once for each distribution
set you wish to install. For instance, if you wish to
install the "base" distribution set, followed by the
"kern" distribution set, and finally the "etc"
distribution set, use the commands:
Extract base
Extract kern
Extract etc
For each extraction, it will ask you if the extraction
should be verbose. If you reply affirmatively, it
will print out the name of each file that's being
extracted.
To install from floppy:
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, enter the command "Set_tmp_dir", and enter
the name of the temporary directory. (Don't forget
that if your disk is still mounted under /mnt; you
should probably pick a directory under /mnt/usr.)
After you have picked a temporary directory, enter the
"Load_fd" command, to load the distribution sets from
your floppies.
You will be asked which floppy drive to use. Enter
"0" (zero) if you're using the first floppy drive
(i.e. what DOS would call "A:"), or enter "1" if
you're using the second.
You will be prompted to insert a floppy into the drive,
to have its contents copied to your hard disk. Do so,
and hit return to begin copying. When that is done,
read the remainder of the floppies that contain the
distribution sets that you want to install, one by
one. When the last is read, and you are being
prompted for another, hit Control-C.
Run the "Extract" command once for each distribution
set you wish to install. For instance, if you wish to
install the "base" distribution set, followed by the
"kern" distribution set, and finally the "etc"
distribution set, use the commands:
Extract base
Extract kern
Extract etc
For each extraction, it will ask you if the extraction
should be verbose. If you reply affirmatively, it
will print out the name of each file that's being
extracted.
(Note: if you know that you will be running low on
disk space when installing NetBSD, you can load and
extract one distribution set at a time. To do this,
load only the floppies which contain the files for the
first distribution set, extract them, and then change
to the temporary directory and remove them with the
command "rm set_name.??".)
Once you are finished extracting all of the sets that
you wish to install, you should proceed to the
instructions below (after the last install medium
type-specific instructions), that explain how you
should configure your system.
To install from tape:
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, enter the command "Set_tmp_dir", and enter
the name of the temporary directory. (Don't forget
that your disk is mounted under /mnt; you should
probably pick a directory under /mnt/usr.) The
default is /mnt/usr/distrib.
After you have picked a temporary directory, enter the
"Load_tape" command, to load the distribution sets from
tape.
You will be asked which tape drive to use. The
default is "rst0", which is correct if you're using
the SCSI tape drive with the lowest SCSI ID number.
(For the SCSI tape drive with the next lowest SCSI ID
number, you should use "rst1", and so on.)
You will be prompted to hit return when you have
inserted the tape into the tape drive. When you do,
the contents of the tape will be extracted into the
temporary directory, and the names of the files being
extracted will be printed.
After the tape has been extracted, to go the directory
containing the first distribution set you wish to
install. (Depending on how you made the tape, it's
probably a subdirectory of the temporary directory you
specified above.) Once there, run the "Set_tmp_dir"
command again, and accept its default answer by
hitting return at the prompt.
Use the "Extract" command to extract the distribution
set. For instance, if you're extracting the "base"
set, use the command:
Extract base
You will be asked if you wish the extraction to be
verbose. If you reply affirmatively, the name of each
file being extracted will be printed.
Repeat the previous two steps for each distribution
set you wish to install. Change to the set's
directory, run "Set_tmp_dir", and then run
"Extract <set_name>" to extract the set.
Once you are finished extracting all of the sets that
you wish to install, you should proceed to the
instructions below (after the last install medium
type-specific instructions), that explain how you
should configure your system.
To install via FTP or NFS:
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, enter the command "Set_tmp_dir", and enter
the name of the temporary directory. (Don't forget
that your disk is mounted under /mnt; you should
probably pick a directory under /mnt/usr.) The
default is /mnt/usr/distrib.
Configure the SLIP interface, with the following
command sequence:
slattach -h -s <speed> tty00
ifconfig sl0 <my_ipaddr> <peer_ipaddr>
where "<speed>" is the network speed, and "<my_ipaddr>"
is the numeric IP address of the machine you are going
to install NetBSD/x68k, while "<peer_ipaddr>" is the
address of the peer machine connected with your machine.
You might have to configure the peer SLIP interface
with similar sequence (depending on the peer system).
For instance, the sequence
slattach -h -s 38400 tty00
ifconfig sl0 192.168.0.1 192.168.0.10
configures the SLIP interface for the network between
your machine (with IP address 192.168.0.1) and the peer
(192.168.0.10) with speed 38400 bps. Note that IP
addresses 192.168.*.* are the private IP addresses
described in RFC 1597.
If you are NFS-mounting the distribution sets, mount
them on the temporary directory with a command like:
mount -t nfs <serv_ipaddr>:<dist_dir> <tmp_dir>
where <serv_ipaddr> is the server's numeric IP address,
<dist_dir> is the path to the distribution files on
the server, and <tmp_dir> is the name of the local
temporary directory.
Once this is done, proceed as if you had loaded the
files from tape, changing to the appropriate
directories, running "Set_tmp_dir", and running
"Extract" as appropriate.
If you are retrieving the distribution sets using ftp,
change into the temporary directory, and execute the
command:
ftp <serv_ipaddr>
where <serv_ipaddr> is once again the server's numeric
IP address. Get the files with FTP, taking care to
use binary mode when transferring the files.
Once you have all of the files for the distribution
sets that you wish to install, you can proceed using
the instructions above, as if you had installed from a
floppy. (Note that as with the floppy install, if
you're short on disk space, you can transfer only one
set at a time, extract it, then delete it, to save
space.)
Once you have finished extracting all of the distribution sets
that you wish to install, and are back at the "#" prompt, you
are ready to configure your system. The configuration utility
expects that you have installed the "base" and "etc"
distribution sets. If you have not, you will not be able to
run it successfully (nor will you have a functional system, in
any case). To configure your newly-installed NetBSD system,
run the command "Configure". It will ask you for the system's
host name, domain name, and other network configuration
information. It will set up your configuration files and make
the device nodes for the newly-installed system.
Congratulations, you have successfully installed NetBSD 1.3.3. When you
reboot into NetBSD, you should log in as "root" at the login prompt.
There is no initial password, but if you're using the machine in a
networked environment, you should create yourself an account and
protect it and the "root" account with good passwords.
Some of the files in the NetBSD 1.3.3 distribution might need to be
tailored for your site. In particular, the /etc/sendmail.cf file will
almost definitely need to be adjusted, and other files in /etc
including /etc/rc.conf will probably need to be modified, as well. If
you are unfamiliar with UN*X-like system administration, it's
recommended that you buy a book that discusses it.
Upgrading a previously-installed NetBSD System:
--------- - ---------- --------- ------ ------
The upgrade to NetBSD 1.3.3 is a binary upgrade; it can be quite difficult
to advance to a later version by recompiling from source due primarily
to interdependencies in the various components.
To do the upgrade, you must have the bootable install floppy
(boot.fs). You must also have at least the "base.tgz" and "kern.tgz"
binary distribution sets available, so that you can upgrade with it,
using one of the upgrade methods described below. Finally, you must
have sufficient disk space available to install the new binaries.
Since the old binaries are being overwritten in place, you only need
space for the new binaries, which weren't previously on the system.
If you have a few megabytes free on each of your root and /usr
partitions, you should have enough space.
Since upgrading involves replacing the boot blocks on your NetBSD
partition, the kernel, and most of the system binaries, it has the
potential to cause data loss. You are strongly advised to BACK UP ANY
IMPORTANT DATA ON YOUR DISK, whether on the NetBSD partition or on
another operating system's partition, before beginning the upgrade
process.
To upgrade your system, follow the following instructions:
Boot your machine using of the boot.fs floppy.
While booting, you will probably see several warnings. You
should be warned that no swap space is present, and that
init(8) cannot find /etc/rc. Do not be alarmed, these are
completely normal. When you reach the prompt asking you for a
shell name, just hit return. Note that once it booted, you
may remove the floppy from the drive.
You will be presented with some information about the upgrade
process and a warning message, and will be asked if you wish
to proceed with the upgrade process. If you answer
negatively, the upgrade process will stop, and your disk will
not be modified. If you answer affirmatively, the upgrade
process will begin, and your disk will be modified. You may
hit Control-C to stop the upgrade process at any time.
However, if you hit it at an inopportune moment, your system
may be left in an inconsistent (and possibly unusable) state.
You will be asked if you wish to upgrade your file systems to
the new file system format. If you do, reply affirmatively.
If you don't have your file systems upgraded now, you should
probably do it manually after the install process is complete,
by using "fsck -c 2". Read the fsck(8) manual page for more
details. Note that this step is only important when upgrading
from a pre-NetBSD 1.0 release.
The upgrade program will then check your root file system,
and, if you approved, will upgrade it to the new file system
format. It will then mount your root file system on /mnt.
If your file systems are being upgraded, the upgrade script
will copy the new fsck(8) program to your hard disk and
upgrade your remaining file systems.
The upgrade program will then automatically replace the boot
blocks on your disk with newer versions, and mount all of your
file systems under /mnt. (In other words, your root partition
will be mounted on /mnt, your /usr partition on /mnt/usr, etc.)
If you don't already have the NetBSD distribution sets on your
disk, look in the installation section for information on how
to transfer them to your disk.
If you don't have the disk space to copy all of the
distribution onto the hard drive, you can do the following:
Install a kernel on the hard drive as detailed a few
paragraphs below, then boot off the hard drive. Now
you can copy and install distribution sets
incrementally from your lone floppy drive.
Once the distribution sets are transferred to your disk,
continue here. (Obviously, if the NetBSD distribution sets
are already on your disk, because you've transferred them
before starting the upgrade process, you don't need to
transfer them again now!)
After the software has been transferred to the machine (or
mounted, in the case of upgrading via NFS or CD-ROM), change
into the directory containing the "base.tgz" distribution set.
Once you are there, run the "Set_tmp_dir" command, and hit
return at the prompt to select the default answer for the
temporary directory's path name. (It should be the path name
of the directory that you're in.)
Run the command "Extract kern" to upgrade the kernel.
Run the command "Extract base" to upgrade the base
distribution.
Repeat the above two steps for all of the sets you wish to
upgrade. (For each, change into the directory containing the
set, run "Set_tmp_dir" and accept the default path name, then
run the "Extract <setname>" command.)
If you were previously using the security distribution set,
you MUST upgrade to the new version, or you will not be able
to log in when the upgrade process is complete. Similarly, if
you were not previously using the security set, you must NOT
upgrade to the new version.
When you are done upgrading all of the distribution sets you
wish to upgrade, issue the command "Cleanup". It will clean
up the installation, by remaking some system databases. When
it is complete, all you have to do is to reboot(8) your system.
Your system has now been upgraded to NetBSD 1.3.3.
After a new kernel has been copied to your hard disk, your
machine is a complete NetBSD 1.3.3 system. However, that
doesn't mean that you're finished with the upgrade process.
There are several things that you should do, or might have to
do, to insure that the system works properly.
First, if you did not upgrade your file systems to the new
file system format during the upgrade process, and you are
upgrading from a pre-1.0 NetBSD, you may want to do so now,
with "fsck -c 2". If you are unsure about the process, it's
suggested that you read the fsck(8) manual page.
Second, you will probably want to get the etc distribution,
extract it, and compare its contents with those in your /etc/
directory. You will probably want to replace some of your
system configuration files, or incorporate some of the changes
in the new versions into yours.
Third, you will probably want to update the set of device
nodes you have in /dev. If you've changed the contents of
/dev by hand, you will need to be careful about this, but if
not, you can just cd into /dev, and run the command "sh
MAKEDEV all".
Fourth, you must deal with certain changes in the formats of
some of the configuration files. The most notable change is
that the "options" given to many of the file systems in
/etc/fstab or by hand have changed, and some of the file
systems have changed names. *IMPORTANT*: ANY INSTANCES OF "ufs"
IN /etc/fstab MUST BE CHANGED TO "ffs". To find out what the
new options are, it's suggested that you read the manual page
for the file systems' mount commands, for example mount_nfs(8)
for NFS. (Note that the information for mounts of type "ffs",
i.e. Fast File Systems, are contained in the mount(8) man
page.)
Finally, you will want to delete old binaries that were part
of the version of NetBSD that you upgraded from and have since
been removed from the NetBSD distribution. If you are
upgrading from a pre-1.0 NetBSD, you might also
want to recompile any locally-built binaries, to take
advantage of the shared libraries. (Note that any new
binaries that you build will be dynamically linked, and
therefore take advantage of the shared libraries, by default.
For information on how to make statically linked binaries,
see the cc(1) and ld(1) manual pages.)
Compatibility Issues With Previous NetBSD Releases:
------------- ------ ---- -------- ------ --------
Users upgrading from previous versions of NetBSD may wish to bear the
following problems and compatibility issues in mind when upgrading to
NetBSD 1.3.3:
* Swap configuration
Description:
All swap partitions are now configured by the swapctl(8)
program. The kernel no longer configures a "default" swap
partition. Because of this, all swap partitions (even the old
"default") must be listed in /etc/fstab.
Many users of previous releases relied on the kernel
configuring a "default" swap partition and did not list any
swap space in /etc/fstab at all -- such users will now have no
swap space configured unless they list swap partitions in
/etc/fstab!
Common symptoms of of this problem include machine crashes
during builds, and similar memory intensive activities.
Fix:
The most common position for a swap partition is the `b'
partition of the drive the root file system is on. For
diskless systems, check the new swapctl(8) manual for more
detail on how this is done. Example fstab entries:
/dev/sd0b none swap sw,priority=0
/dev/sd1b none swap sw,priority=5
* NFS daemons and other programs in /sbin moved
Description:
The NFS daemons (nfsd, nfsiod, mountd) have been moved from
the /sbin to the /usr/sbin directory. When new binaries are
loaded over old ones during upgrade, most programs get
overlaid and replaced, but unless these binaries are
explicitly removed they will not disappear. The installation
subsystems on some NetBSD architectures will not properly
remove these binaries.
Due to changes in the NFS subsystem, the old NFS daemon
binaries will not work correctly, and will cause serious
problems. Unfortunately, the default startup script (/etc/rc)
will run the old binaries in /sbin if they are present instead
of the new ones in /usr/sbin.
Some other programs (dumpfs, dumplfs and quotacheck) have also
been moved from /sbin to /usr/sbin, and old versions may be
left behind by accident. They, too, may cause difficulties.
Fix:
Remove the old daemon binaries (/sbin/nfsiod, /sbin/nfsd,
/sbin/mountd, etc.) after your upgrade has finished. You may
wish to do an "ls -lt /sbin | more" to help determine which
binaries were not replaced/removed during your upgrade.
* AMANDA, The Advanced Maryland Automatic Network Disk Archiver,
from http://www.amanda.org
Description:
Due to a change in the output of dump(8) to ensure
consistency in the messages, AMANDA's dump output
parser breaks.
Error messages such as the following may be an
indication that this problem is present:
FAILURE AND STRANGE DUMP SUMMARY:
hostname wd0e lev 1 FAILED [no backup size line]
Versions affected:
2.3.0.4, and most likely earlier versions
Workaround/Fix:
One of:
* Apply the patch found at:
ftp://ftp.netbsd.org/pub/NetBSD/misc/patches/amanda-pre-2.4.patch
* Upgrade to AMANDA 2.4.0 or newer. The side effect of this is
that the network protocol is incompatible with earlier
versions.
Using online NetBSD documentation
----- ------ ------ -------------
Documentation is available if you first install the manual
distribution set. Traditionally, the "man pages" (documentation)
are denoted by 'name(section)'. Some examples of this are
intro(1),
man(1),
apropros(1),
passwd(1), and
passwd(5).
The section numbers group the topics into several categories, but three
are of primary interest: user commands are in section 1, file formats
are in section 5, and administrative information is in section 8.
The 'man' command is used to view the documentation on a topic, and is
started by entering 'man [section] topic'. The brackets [] around the
section should not be entered, but rather indicate that the section is
optional. If you don't ask for a particular section, the topic with the
least-numbered section name will be displayed. For instance, after
logging in, enter
man passwd
to read the documentation for passwd(1). To view the documentation for
passwd(5), enter
man 5 passwd
instead.
If you are unsure of what man page you are looking for, enter
apropos subject-word
where "subject-word" is your topic of interest; a list of possibly
related man pages will be displayed.
Administrivia:
-------------
If you've got something to say, do so! We'd like your input.
There are various mailing lists available via the mailing list
server at <majordomo@NetBSD.ORG>. To get help on using the mailing
list server, send mail to that address with an empty body, and it will
reply with instructions.
There are various mailing lists set up to deal with comments and
questions about this release. Please send comments to:
netbsd-comments@NetBSD.ORG
To report bugs, use the 'send-pr' command shipped with NetBSD,
and fill in as much information about the problem as you can. Good
bug reports include lots of details. Additionally, bug reports can
be sent by mail to:
netbsd-bugs@NetBSD.ORG
Use of 'send-pr' is encouraged, however, because bugs reported with it
are entered into the NetBSD bugs database, and thus can't slip through
the cracks.
There are also port-specific mailing lists, to discuss aspects of
each port of NetBSD. Use majordomo to find their addresses. If
you're interested in doing a serious amount of work on a specific
port, you probably should contact the "owner" of that port (listed
below).
If you'd like to help with this effort, and have an idea as to how
you could be useful, send mail and/or subscribe to:
netbsd-help@NetBSD.ORG
As a favor, please avoid mailing huge documents or files to these
mailing lists. Instead, put the material you would have sent up
for FTP somewhere, then mail the appropriate list about it, or, if
you'd rather not do that, mail the list saying you'll send the data
to those who want it.
Thanks go to:
------ -- --
Members and former members of UCB's Computer Systems Research Group,
including (but not limited to):
Keith Bostic
Ralph Campbell
Mike Karels
Marshall Kirk McKusick
for their ongoing work on BSD systems, support, and encouragement.
Also, our thanks go to:
Mike Hibler
Rick Macklem
Jan-Simon Pendry
Chris Torek
for answering lots of questions, fixing bugs, and doing the various work
they've done.
UC Berkeley's Experimental Computing Facility provided a home for
sun-lamp in the past, people to look after it, and a sense of humor.
Rob Robertson, too, has added his unique sense of humor to things, and
for a long time provided the primary FTP site for NetBSD.
Best Internet Communications for hosting the NetBSD FTP and SUP server.
Cygnus Support for hosting the NetBSD Mail server.
Without CVS, this project would be impossible to manage, so our hats
go off to Brian Berliner, Jeff Polk, and the various other people
who've had a hand in making CVS a useful tool.
Dave Burgess <burgess@cynjut.infonet.net> has been maintaining the
386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be
recognized for it.
The following people (in alphabetical order) have made donations or
loans of hardware and/or money, to support NetBSD development, and
deserve credit for it:
Bay Area Internet Solutions
Jason Brazile
David Brownlee
Simon Burge
Dave Burgess
Ralph Campbell
Canada Connect Corporation
Brian Carlstrom
James Chacon
Bill Coldwell
Charles Conn
Tom Coulter
Charles D. Cranor
Christopher G. Demetriou
Demon Internet, UK
Easynet, UK
Scott Ellis
Free Hardware Foundation
Greg Gingerich
Michael L. Hitch
Innovation Development Enterprises of America
Scott Kaplan
Chris Legrow
Neil J. McRae
Perry E. Metzger
MS Macro System GmbH, Germany
Numerical Aerospace Simulation Facility, NASA Ames Research Center
Herb Peyerl
Mike Price
Thor Lancelot Simon
Bill Sommerfeld
Paul Southworth
Jason R. Thorpe
Steve Wadlow
(If you're not on that list and should be, tell us! We probably were
not able to get in touch with you, to verify that you wanted to be
listed.)
Finally, we thank all of the people who've put sweat and tears into
developing NetBSD since its inception in January, 1993. (Obviously,
there are a lot more people who deserve thanks here. If you're one of
them, and would like to mentioned, tell us!)
We are:
-- ---
(in alphabetical order)
The NetBSD core group:
Paul Kranenburg <pk@NetBSD.ORG>
Herb Peyerl <hpeyerl@NetBSD.ORG>
Scott Reynolds <scottr@NetBSD.ORG)
Jason Thorpe <thorpej@NetBSD.ORG>
Christos Zoulas <christos@NetBSD.ORG>
The port-masters (and their ports):
Mark Brinicombe <mark@NetBSD.ORG> (arm32)
Jeremy Cooper <jeremy@NetBSD.ORG> (sun3x)
Chuck Cranor <chuck@NetBSD.ORG> (mvme68k)
Charles Hannum <mycroft@NetBSD.ORG> (i386)
Ross Harvey <ross@NetBSD.ORG> (alpha)
Chris Hopps <chopps@NetBSD.ORG> (amiga)
Eduardo Horvath <eeh@NetBSD.ORG> (sparc64)
Paul Kranenburg <pk@NetBSD.ORG> (sparc)
Ted Lemon <mellon@NetBSD.ORG> (pmax)
Anders Magnusson <ragge@NetBSD.ORG> (vax)
Tsubai Masanari <tsubai@NetBSD.ORG> (macppc, newsmips)
Phil Nelson <phil@NetBSD.ORG> (pc532)
Masaru Oki <oki@NetBSD.ORG> (x68k)
Scott Reynolds <scottr@NetBSD.ORG> (mac68k)
Gordon Ross <gwr@NetBSD.ORG> (sun3, sun3x)
Kazuki Sakamoto <sakamoto@NetBSD.ORG> (bebox)
Wolfgang Solfrank <ws@NetBSD.ORG> (powerpc)
Jonathan Stone <jonathan@NetBSD.ORG> (pmax)
Jason Thorpe <thorpej@NetBSD.ORG> (hp300)
Frank van der Linden <fvdl@NetBSD.ORG> (i386)
Leo Weppelman <leo@NetBSD.ORG> (atari)
The NetBSD 1.3.3 Release Engineering team:
Chris G. Demetriou <cgd@NetBSD.ORG>
Ted Lemon <mellon@NetBSD.ORG>
Perry Metzger <perry@NetBSD.ORG>
Jason Thorpe <thorpej@NetBSD.ORG>
Supporting cast:
Steve Allen <wormey@NetBSD.ORG>
Lennart Augustsson <augustss@NetBSD.ORG>
Christoph Badura <bad@NetBSD.ORG>
Manuel Bouyer <bouyer@NetBSD.ORG>
Robert V. Baron <rvb@NetBSD.ORG>
John Birrell <jb@NetBSD.ORG>
Manuel Bouyer <bouyer@NetBSD.ORG>
John Brezak <brezak@NetBSD.ORG>
Allen Briggs <briggs@NetBSD.ORG>
Aaron Brown <abrown@NetBSD.ORG>
David Brownlee <abs@NetBSD.ORG>
Simon Burge <simonb@NetBSD.ORG>
Dave Burgess <burgess@cynjut.infonet.net>
Dave Carrel <carrel@NetBSD.ORG>
Bill Coldwell <billc@NetBSD.ORG>
Alistair Crooks <agc@NetBSD.ORG>
Aidan Cully <aidan@NetBSD.ORG>
Rob Deker <deker@NetBSD.ORG>
Chris G. Demetriou <cgd@NetBSD.ORG>
Matthias Drochner <drochner@NetBSD.ORG>
Enami Tsugutomo <enami@NetBSD.ORG>
Bernd Ernesti <veego@NetBSD.ORG>
Erik Fair <fair@NetBSD.ORG>
Hubert Feyrer <hubertf@NetBSD.ORG>
Thorsten Frueauf <frueauf@NetBSD.ORG>
Brian R. Gaeke <brg@dgate.org>
Thomas Gerner <thomas@NetBSD.ORG>
Justin Gibbs <gibbs@NetBSD.ORG>
Adam Glass <glass@NetBSD.ORG>
Michael Graff <explorer@NetBSD.ORG>
Brad Grantham <grantham@tenon.com>
Matthew Green <mrg@NetBSD.ORG>
Juergen Hannken-Illjes <hannken@NetBSD.ORG>
Charles M. Hannum <mycroft@NetBSD.ORG>
Eric Haszlakiewicz <erh@NetBSD.ORG>
Michael L. Hitch <osymh@NetBSD.ORG>
Ken Hornstein <kenh@NetBSD.ORG>
Marc Horowitz <marc@NetBSD.ORG>
ITOH Yasufumi <itohy@NetBSD.ORG>
Matthew Jacob <mjacob@NetBSD.ORG>
Lonhyn T. Jasinskyj <lonhyn@NetBSD.ORG>
Darrin Jewell <dbj@NetBSD.ORG>
Lawrence Kesteloot <kesteloo@cs.unc.edu>
Klaus Klein <kleink@NetBSD.ORG>
John Kohl <jtk@NetBSD.ORG>
Kevin Lahey <kml@NetBSD.ORG>
Ted Lemon <mellon@NetBSD.ORG>
Mike Long <mikel@NetBSD.ORG>
Paul Mackerras <paulus@NetBSD.ORG>
Neil J. McRae <neil@NetBSD.ORG>
Perry Metzger <perry@NetBSD.ORG>
Luke Mewburn <lukem@NetBSD.ORG>
Minoura Makoto <minoura@NetBSD.ORG>
der Mouse <mouse@NetBSD.ORG>
Tohru Nishimura <nisimura@NetBSD.ORG>
Greg Oster <oster@NetBSD.ORG>
Herb Peyerl <hpeyerl@NetBSD.ORG>
Matthias Pfaller <matthias@NetBSD.ORG>
Dante Profeta <dante@NetBSD.ORG>
Chris Provenzano <proven@NetBSD.ORG>
Waldi Ravens <waldi@moacs.indiv.nl.net>
Darren Reed <darrenr@NetBSD.ORG>
Tim Rightnour <garbled@NetBSD.ORG>
Heiko W. Rupp <hwr@NetBSD.ORG>
SAITOH Masanobu <msaitoh@NetBSD.ORG>
Kazuki Sakamoto <sakamoto@NetBSD.ORG>
Curt Sampson <cjs@NetBSD.ORG>
Wilfredo Sanchez <wsanchez@NetBSD.ORG>
Ty Sarna <tsarna@NetBSD.ORG>
Matthias Scheler <tron@NetBSD.ORG>
Karl Schilke (rAT) <rat@NetBSD.ORG>
Tim Shepard <shep@NetBSD.ORG>
Chuck Silvers <chs@NetBSD.ORG>
Thor Lancelot Simon <tls@NetBSD.ORG>
Noriyuki Soda <soda@NetBSD.ORG>
Wolfgang Solfrank <ws@NetBSD.ORG>
Bill Sommerfeld <sommerfeld@NetBSD.ORG>
Ignatios Souvatzis <is@NetBSD.ORG>
Bill Studenmund <wrstuden@NetBSD.ORG>
Kevin Sullivan <sullivan@NetBSD.ORG>
Kimmo Suominen <kim@NetBSD.ORG>
Matt Thomas <matt@NetBSD.ORG>
Christoph Toshok <toshok@NetBSD.ORG>
Todd Vierling <tv@NetBSD.ORG>
Paul Vixie <vixie@NetBSD.ORG>
Krister Walfridsson <kristerw@NetBSD.ORG>
Nathan Williams <nathanw@NetBSD.ORG>
Colin Wood <ender@NetBSD.ORG>
Steve Woodford <scw@NetBSD.ORG>
Dedication:
----------
The Release Engineering team would like to dedicate the NetBSD 1.3
release to the memory of the late Koji Imada, who was killed in a
motorcycle accident in August, 1997 at the age of 28. A doctoral
student in Mathematical Science at Nagoya University, he was a user of
NetBSD and a contributor to the project since 1993. Well remembered by
his friends, he was also known as a connoisseur of gins, teas, and the
motorcycles he loved to ride. His death came as a shock, and he will
be greatly missed by all of us. May he rest in peace.
Legal Mumbo-jumbo:
----- ----- -----
The following notices are required to satisfy the license terms of
the software that we have mentioned in this document:
This product includes software developed by the University of
California, Berkeley and its contributors.
This product includes software developed by the Computer
Systems Engineering Group at Lawrence Berkeley Laboratory.
This product includes software developed by the NetBSD
Foundation, Inc. and its contributors.
This product includes software developed by Adam Glass
and Charles Hannum.
This product includes software developed by Adam Glass.
This product includes software developed by Berkeley Software
Design, Inc.
This product includes software developed by Charles D. Cranor
and Washington University.
This product includes software developed by Charles D. Cranor.
This product includes software developed by Charles Hannum,
by the University of Vermont and State Agricultural College
and Garrett A. Wollman, by William F. Jolitz, and by the
University of California, Berkeley, Lawrence Berkeley Laboratory,
and its contributors.
This product includes software developed by Charles Hannum.
This product includes software developed by Charles M. Hannum.
This product includes software developed by Chris Provenzano.
This product includes software developed by Christian E. Hopps.
This product includes software developed by Christopher G. Demetriou
for the NetBSD Project.
This product includes software developed by Christopher G. Demetriou.
This product includes software developed by Christos Zoulas.
This product includes software developed by David Jones and Gordon Ross.
This product includes software developed by Dean Huxley.
This product includes software developed by Eric S. Hvozda.
This product includes software developed by Ezra Story.
This product includes software developed by Gordon Ross.
This product includes software developed by Gordon W. Ross
and Leo Weppelman.
This product includes software developed by Gordon W. Ross.
This product includes software developed by Herb Peyerl.
This product includes software developed by Ian W. Dall.
This product includes software developed by Ignatios Souvatzis
for the NetBSD Project.
This product includes software developed by Jason R. Thorpe
for And Communications, http://www.and.com/.
This product includes software developed by Joachim Koenig-Baltes.
This product includes software developed by Jochen Pohl
for The NetBSD Project.
This product includes software developed by John Polstra.
This product includes software developed by Jonathan Stone
and Jason R. Thorpe for the NetBSD Project.
This product includes software developed by Jonathan Stone
for the NetBSD Project.
This product includes software developed by Jonathan Stone.
This product includes software developed by Julian Highfield.
This product includes software developed by Kenneth Stailey.
This product includes software developed by Leo Weppelman.
This product includes software developed by Lloyd Parkes.
This product includes software developed by Mark Brinicombe.
This product includes software developed by Markus Wild.
This product includes software developed by Martin Husemann
and Wolfgang Solfrank.
This product includes software developed by Mats O Jansson
and Charles D. Cranor.
This product includes software developed by Mats O Jansson.
This product includes software developed by Matthias Pfaller.
This product includes software developed by Paul Kranenburg.
This product includes software developed by Paul Mackerras.
This product includes software developed by Peter Galbavy.
This product includes software developed by Philip A. Nelson.
This product includes software developed by Rodney W. Grimes.
This product includes software developed by Scott Bartram.
This product includes software developed by SigmaSoft, Th.
This product includes software developed by Terrence R. Lambert.
This product includes software developed by Theo de Raadt
and John Brezak.
This product includes software developed by Theo de Raadt.
This product includes software developed by TooLs GmbH.
This product includes software developed by Winning Strategies, Inc.
This product includes software developed by the Center for
Software Science at the University of Utah.
This product includes software developed by the University of Calgary
Department of Computer Science and its contributors.
This product includes software developed by the University of Vermont
and State Agricultural College and Garrett A. Wollman.
This product includes software developed for the FreeBSD project.
This product includes software developed for the Internet
Software Consortium by Ted Lemon.
This product includes software developed for the NetBSD Project
by Frank van der Linden.
This product includes software developed for the NetBSD Project
by Jason R. Thorpe.
This product includes software developed for the NetBSD Project
by John M. Vinopal.
This product includes software developed for the NetBSD Project
by Matthias Drochner.
This product includes software developed for the NetBSD Project
by Matthieu Herrb.
This product includes software developed for the NetBSD Project
by Perry E. Metzger.
This product includes software developed for the NetBSD Project
by Piermont Information Systems Inc.
This product includes software developed for the NetBSD Project
by Ted Lemon.
This product includes software developed by Masaru Oki.
This product includes software developed by Masanobu Saitoh.
This product includes software developed by Takumi Nakamura.
This product includes software developed by Kazuhisa Shimizu.
This product includes software developed by Takuya HARAKAWA.
This product includes software developed by MINOURA Makoto.
This product includes software developed by Yasushi YAMASAKI.
This product includes software developed by ITOH Yasufumi.